Java API for XML Registries (JAXR) provider for UDDI

The Java™ API for XML Registries (JAXR) is a Java client API for accessing both UDDI (Version 2 only) and ebXML registries. It is part of the Java Platform, Enterprise Edition (Java EE) specification.

Deprecated feature: From WebSphere® Application Server Version 8.0, Java API for XML Registries (JAX-R) APIs are deprecated. The Java Platform, Enterprise Edition (Java EE) 6 platform began the deprecation process for JAX-R because it is based on Universal Description, Discovery and Integration (UDDI) 2 technology, which is no longer relevant. If your applications use JAX-R, then you might consider using UDDI 3.

The JAXR API comprises the Java EE packages javax.xml.registry and javax.xml.registry.infomodel. Java EE API documentation is at Web Services Reference.

The preferred UDDI Java client APIs are:
  • UDDI4J Version 2, for UDDI Version 2
  • UDDI Version 3 Client for Java, for UDDI Version 3

JAXR provider

The current JAXR specification (Version 1.0) defines a JAXR provider as an implementation of the JAXR API. Generally, a JAXR provider can be a JAXR provider for UDDI, a JAXR provider for ebXML, or a pluggable provider that supports both UDDI and ebXML. The JAXR provider for UDDI is a provider for UDDI only.

UDDI versions

A JAXR provider for UDDI accesses a UDDI registry that uses the UDDI Version 2 SOAP APIs only. The UDDI registry for UDDI Version 3 in this version of WebSphere Application Server supports the UDDI Version 1, 2 and 3 SOAP APIs. Therefore you can use the JAXR provider for UDDI to access this registry. You can also use the JAXR provider to access the UDDI registry for UDDI Version 2 in WebSphere Application Server Version 5.x.

To work with the UDDI Version 3 SOAP APIs, use the UDDI Version 3 Client for Java; you cannot use JAXR.

Capability level

The JAXR specification defines two capability profiles, capability level 0 and capability level 1. The JAXR API documentation categorizes each JAXR method as either level 0 or level 1. Generally, a JAXR provider for UDDI has capability level 0 and supports all level 0 methods, whereas a JAXR provider for ebXML has capability level 1 and supports all level 0 and level 1 methods. The JAXR provider for UDDI is a capability level 0 provider, and supports only level 0 methods.

Authentication and security

The javax.xml.registry.authenticationMethod connection property determines which method the JAXR provider uses to authenticate with the UDDI registry.

The JAXR provider uses UDDI Version 2 SOAP Inquiry and Publish APIs. These APIs are protected, as described in the topic about access control for UDDI registry interfaces.

You can use Secure Sockets Layer (SSL) to encrypt HTTP traffic between the JAXR provider for UDDI and the UDDI registry.